The Hive - Create case

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

↑ Back to Content Index

Once a new Microsoft Sentinel incident is created, this playbook gets triggered and performs the following actions: 1. Creates case in TheHive instance with enriched description and title. 2. Gets Hosts, IPs entities. 3. Creates task and bind it to case. 4. Creates observables with hosts and IPs for created case.

Attribute Value
Type Playbook
Solution TheHive
Source View on GitHub

Additional Documentation

📄 Source: TheHive-CreateCase/readme.md

TheHvie-CreateCase

Summary

When a new sentinel incident is created, this playbook gets triggered and performs the following actions:

  1. Create case in TheHive instance with and enrich it with description and title
  2. Gets Hosts, IPs entities.
  3. Create task and bind it to case.
  4. Creates obsarvebles with hosts and IPs for created case.


Prerequisites

  1. Prior to the deployment of this playbook, TheHive API Connector needs to be deployed under the same subscription.
  2. Obtain TheHive API credentials. Refer to TheHive API Custom Connector documentation.

Deployment instructions

  1. To deploy the Playbook, click the Deploy to Azure button. This will launch the ARM Template deployment wizard.
  2. Fill in the required paramteres:
    • Playbook Name: Enter the playbook name here
    • Connector Name: Enter the Logic App connector name for TheHive here
    • onPremiseGatewayName: Provide the On-premises data gateway that will be used with The Hive connector. Data gateway should be deployed under the same subscription and resource group as playbook.

Deploy to Azure Deploy to Azure

Post-Deployment instructions

a. Authorize connections

Once deployment is complete, authorize each connection.

  1. Click the Microsoft Sentinel connection resource
  2. Click edit API connection
  3. Click Authorize
  4. Sign in
  5. Click Save
  6. Repeat steps for other connections

b. Configurations in Sentinel

  1. In Microsoft Sentinel, analytical rules should be configured to trigger an incident. In the Entity maping section of the analytics rule creation workflow, suspicious IP and hostnames should be mapped to Address identitfier of the IP for IPs entity type and HostName for the Host. Check the documentation to learn more about mapping entities.
  2. Configure the automation rules to trigger the playbook.

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

↑ Back to Playbooks · Back to TheHive